feat(package): provenance support #5275
Closed
+4
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support Provenance Statement
A provenance statement is displayed in a packages' registry page, as shown here:
For more information regarding provenance statements and the requirements as defined by npmjs, see https://docs.npmjs.com/generating-provenance-statements#prerequisites
The
id-token
permission is required to publish to SigStore via OpenID Connect. You can read more about GitHub's attestation program here: https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-buildsGitHub Action CI Support
You can use PNPM, just be sure to use the latest npm client for the actual publishing part of the release process. Yarn is not supported.
Scoped Publishing
Seeing as Hardhat is not scoped under the @NomicFoundation org, packages that are scoped should adjust their configuration in the manifest:
npm audit signatures